Update EmsdkPackageVersion to use version from dependency flow#128261
Conversation
It got hardcoded a while ago to workaround a build problem.
There was a problem hiding this comment.
Pull request overview
This PR updates the build’s Emscripten SDK provisioning versioning so it no longer relies on a hardcoded EmsdkPackageVersion value in eng/Versions.props, instead sourcing it from a dependency-flow-updated property.
Changes:
- Replace the hardcoded
EmsdkPackageVersion(10.0.0) with$(MicrosoftDotNetApiCompatTaskPackageVersion). - Add an explanatory comment about why a stable, dependency-flow-backed version property is used.
This comment has been minimized.
This comment has been minimized.
|
Caution Security scanning requires review for Code Review DetailsThe threat detection results could not be parsed. The workflow output should be reviewed before merging. Review the workflow run logs for details. Note This review was generated by Copilot. 🤖 Copilot Code Review — PR #128261Holistic AssessmentMotivation: Justified — removing a hardcoded version ( Approach: Correct — uses Summary: ✅ LGTM. Single-property change in Detailed Findings✅ Correctness — Version source is appropriate
✅ Consistency — Follows established patternThe adjacent ✅ Scope — Minimal and focusedOnly one property value changed, with appropriate explanatory comments added. No risk of unintended side effects.
|
|
/ba-g known issues (BA didn't match it due to build timeouts) |
It got hardcoded a while ago to workaround a build problem.